Columbia Kermit/kermit.zip/newsgroups/misc.20000824-20010305/[e-mail] _Wed Oct 4 22:09:08 2000.msg

Internet Message Format | 2020-01-01 | 5KB

Return-Path: <[e-mail]>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
    by uhaligani.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id WAA02519
    for <[e-mail]>; Wed, 4 Oct 2000 22:09:07 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
    by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id WAA29674
    for <[e-mail]>; Wed, 4 Oct 2000 22:09:07 -0400 (EDT)
Received: (from news@localhost)
    by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id VAA04960
    for [e-mail]; Wed, 4 Oct 2000 21:41:34 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: "Steve" <[e-mail]>
Subject: Re: No Carrier
Message-ID: <y_QC5.4768$[e-mail]>
Organization: Giganews.Com - Premium News Outsourcing
Date: Thu, 05 Oct 2000 01:40:46 GMT
To: [e-mail]


Jeffrey Altman <[e-mail]> wrote in message
news:8rgbe1$q2h$[e-mail]...
> In article <YaOC5.4391$[e-mail]>,
> Steve <[e-mail]> wrote:
> : I have software that runs on DOS computers that uses Kermit 3.15 to
transfer
> : files to a server running a DOS application under Windows 95 also using
> : Kermit 3.15.  The DOS computer initiates everything, the connection, the
> : file transfers, etc.  The files are either transferred locally using a
> : serial cable or remotely over a modem.  Everything works fine.  We are
> : trying to switch from 3.15 on the server to K95 to allow multiple
transfers
> : on the same server at a time and have created the server program using
VB.
> : It seems to work fine except over a modem.  After the DOS computer calls
in
> : and connects, the first thing it does is issue a FIN to reset the server
in
> : case the previous transfer did not go to completion.  In the K95 version
> : over a modem, I always get a no carrier on the DOS computer immediately
> : after the FIN as the modem on the server side appears to drop the
> : connection.  I can tell the server did get the FIN and the DOS computer
> : should pause for a couple of seconds before issuing the next command.
> :
> : We are using a shell command to call K95 that looks like:
> :
> : For the modem file transfer the .ini file looks like:
> : set carrier off
> : set port 1
> : set speed 9600
> : set incomplete discard
> : set send packet 94
> : set retry 60
> : set flow xon/xoff
> : set handshake none
> : set duplex full
> : output AT s0=1\13
> : output AT s37=9\13
> : server
> : exit
> :
> : The dial string we use on the DOS computer side is:
> : output AT&F&C0&D1s37=9N0DT [phone number]\13
> :
> : Any ideas on why I am dropping the line?  Any suggestions on better
settings
> : on either the server or DOS side?
> :
> : Thanks,
> : Steve
>
> The FINISH command sent by the client and received by the SERVER causes
> the SERVER command to terminate.  Therefore, the EXIT command is executed
> and the K95 session terminates hanging up the modem
>
> There is no need for the FINISH command to be sent, if the previous
> session was closed prematurely by the client the SERVER command would
> be automaticly terminated when the carrier signal was lost by the modem.
>
> Also, instead of using OUTPUT AT ... just configure the modem with the
> proper SET MODEM TYPE command and use the ANSWER command to receive the
> incoming call.
>
>                   Jeffrey Altman * Sr.Software Designer
>                  The Kermit Project * Columbia University
>                612 West 115th St * New York, NY * 10025 * USA
>      http://www.kermit-project.org/ * [e-mail]

The reason for the exit in the .ini after the server is before we put it in,
when we would FIN on the DOS client, the server would go to the K95> prompt.
We originally invoked K95 by shelling out using:
k95 -l Com2  -b 9600 -x
Then for flexibility purposes we thought we could use an ini file so we
changed the command line to:
k95 -y IniFileName

This is where we started running into the K95> prompt issue.  I have since
changed to:
k95 -y IniFileName -x
and have taken out the server and exit lines of the .ini but am still
getting the no carrier, even when I try the set modem type and the answer.
The modem I am testing with is a Cnet 56K, not sure what modem type I should
specify, I have been telling it generic-high-speed.

Is the FIN what is causing the no carrier?  If so that is going to be a
problem as I doubt we can update the clients to change this.  If I am
running the server command in 3.15 instead of K95 and send a FIN from the
DOS client all the time and it does not drop the line.  Is this a change
with K95?

FYI...This may give you a better idea of how the server software works:

DO
    Do Until Client ID File is received
        Change to generic receive directory
        K95 server (receive client ID file)
    End Do

    Open ID File, get Client ID
    Change to client specific directory
    K95 server (receive client data files)
    Process client data files

End Do

Any thoughts?
Steve